Vcenter Namespaces Instances SharedSubnet
The Vcenter Namespaces Instances SharedSubnet schema defines the information for a Subnet shared with a vSphere Namespace.
This schema was added in vSphere API 9.1.0.0.
{
"path": "string",
"pod_default": false,
"vm_default": false,
"name": "string"
}
NSX path of the shared Subnet created outside of the Supervisor to be associated with this vSphere Namespace.
This property was added in vSphere API 9.1.0.0.
Indicates the shared Subnet is used for vSphere Pod default networks in this Namespace.
If the shared Subnet is specified to be used for vSphere Pod default networks, com.vmware.vcenter.namespaces.VpcNetworkCreateSpec#vpc must also be specified since shared Subnets for vSphere Pods need to match the vSphere Namespace's VPC to create resources like Load Balancer Virtual Services and Static Routes.
This property was added in vSphere API 9.1.1.0.
If missing or null, the shared Subnet is not used for vSphere Pod default networks.
If no shared Subnets are specified as Pod default networks and there is PrivateTGW IPBlock with sufficient space in the Namespace's VPC, the Pod default network will use Subnets generated from the IPBlock. Otherwise, Pods are not assigned a default network.
Indicates the shared Subnet is used for VM default networks in this Namespace.
If the shared Subnet is specified to be used for VM default networks, com.vmware.vcenter.namespaces.VpcNetworkCreateSpec#vpc must also be specified since shared Subnets for VMs need to match the vSphere Namespace's VPC to create resources like Load Balancer Virtual Services and Static Routes.
This property was added in vSphere API 9.1.1.0.
If missing or null, the shared Subnet is not used for VM default networks.
If no shared Subnets are specified as VM default networks and there is PrivateCIDRs with sufficient space in the Namespace's VPC, the VM default network will use Subnets generated from PrivateCIDRs. Otherwise, there will be no VM default network.
Name of the shared Subnet that can be used to reference this object. After creation, the name cannot be updated. This must be a valid DNS subdomain name as defined in RFC 1123. It must:
- have a maximum length of 253 characters
- contain only lowercase alphanumeric characters, '-', or '.'
- start and end with an alphanumeric character This name must also be unique within a vSphere Namespace.
This property was added in vSphere API 9.1.1.0.
If missing or null, a non-conflicting and valid DNS subdomain name will be generated.